Sub-topology discovery for operating hybrid solutions

ABSTRACT

Network topology information may be determined for a plurality of network devices on a network. System identifier information may then be determined for each of the plurality of network devices on the network. The system identifier information may be a list of network solutions that each network device actually or potentially belongs to. The system may then flag the system identifier information to indicate whether each solution is an actual or a potential solution.

RELATED APPLICATION

This application is a division of co-pending U.S. application Ser. No.15,279,469 entitled “Sub-Topology Discovery for Operating HybridSolutions” filed Sep. 29, 2016, which is a division of U.S. applicationSer. No. 13/289,330 entitled “Sub-Topology Discovery for OperatingHybrid Solutions” filed Nov. 4, 2011, now U.S. Pat. No. 9,497,081,issued Nov. 15, 2016, both are entirely incorporated herein byreference.

BACKGROUND

System identifiers may be defined such that devices may be identified asto whether they are operating as part of a specific operating hybridsolution. A device may be queried to find out their associated “systemid”. However, the nature of operating hybrid solutions (or “systems”) issuch that it may be a multi-device sub-topology (or logical topology)over a network. As such, there is a need to determine the specificsub-topology that is capable (or configured) for a particular operatinghybrid solution.

Furthermore, by definition, operating hybrid solutions may be tied toWhole Offers (“WOs”) in which the actual system is the entity sold andsupported by a vendor. By extension, there also exists a need fordiscovery of a WO within the topology.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings, which are incorporated in and constitute apart of this disclosure, illustrate various embodiments. In thedrawings:

FIG. 1 is an illustration of an operating environment for embodimentsdescribed herein;

FIG. 2 is a flow chart of embodiments for providing a dynamic space;

FIG. 3 is a flow chart of embodiments for providing a dynamic space;

FIG. 4 is a flow chart of embodiments for providing a dynamic space;

FIG. 5 is a block diagram of a network computing device.

DESCRIPTION OF EXAMPLE EMBODIMENTS Overview

Consistent with embodiments of the present disclosure, systems andmethods are disclosed for sub-topology discovery. For example networktopology information may be determined for a plurality of networkdevices on a network. System identifier information may then bedetermined for each of the plurality of network devices on the network.The system identifier information may be a list of network solutionsthat each network device actually or potentially belongs to. The systemmay then flag the system identifier information to indicate whether eachsolution is an actual or a potential solution.

It is to be understood that both the foregoing general description andthe following detailed description are examples and explanatory only,and should not be considered to restrict the application's scope, asdescribed and claimed. Further, features and/or variations may beprovided in addition to those set forth herein. For example, embodimentsof the present disclosure may be directed to various featurecombinations and sub-combinations described in the detailed description.

DETAILED DESCRIPTION

The following detailed description refers to the accompanying drawings.Wherever possible, the same reference numbers are used in the drawingsand the following description to refer to the same or similar elements.While embodiments of this disclosure may be described, modifications,adaptations, and other implementations are possible. For example,substitutions, additions, or modifications may be made to the elementsillustrated in the drawings, and the methods described herein may bemodified by substituting, reordering, or adding stages to the disclosedmethods. Accordingly, the following detailed description does not limitthe disclosure. Instead, the proper scope of the disclosure is definedby the appended claims.

Embodiments of the present disclosure are configured to work with anymulti-layer topology discovery protocol (e.g., Layer 2, Layer 3, Layer7, etc.). A discovered system identifier may be advertised as aninformation element tied to each particular device or node in: 1)responses to topology discovery queries from a neighbor during atopology discovery protocol crawl; 2) responses to topology discoverypolls from a central server or process such as a Network ManagementSystem (“NMS”) or service process; 3) link state advertisements inlink-state routing protocols such as Open Shortest Path First (“OSPF”);and 4) automatic advertisements, such as Cisco Discovery Protocol(“CDP”). Link-state protocols, or instances of them, may be inherentlytopology discovery protocols in that they allow a node to build atopology map of a network or subnet of which it is a part.

FIG. 1 illustrates a sample operating environment for embodiments of thepresent disclosure. A plurality of nodes (network devices), such as node110, node 120, node 130, and node 140, may be in communication over anetwork 150. Network 150 may comprise any appropriate communicationsnetwork on which a plurality of devices may be in communication with oneanother.

Depending on the determined topology discovery protocol, the discovereddevice or node may be an L2 entity, such as a switch, a wireless LANcontroller (“WLC”), or a wireless access point (“WAP”). Furthermore, thediscovered device or node may be an L3 entity such as a router, an L7entity such as a media endpoint in a MediaNet, an application endpoint,a media server, or an application server. It should be understood thatthe above list is exemplary and other appropriate network devices arecompatible with embodiments of the present disclosure.

Each node may be associated with a system identifier. In someembodiments, the system identifier may comprise a list of solutions(“systems”) (e.g., TrustSec, EnergyWise, MediaNet, etc.) that the nodepotentially or actually belongs to. Each element in the systemidentifier list may be flagged as “potential” or “actual” to indicatewhether the said capability has been configured on the node, or isoperationally active. The system identifier information elementassociated with the topology discovery protocol may correspond to asimilar system identifier data structure within a discovered node.Alternatively, in some embodiments, the system identifier informationelement associated with the topology discovery protocol may be derivedfrom the primary capabilities and configuration data (“operatingcriteria”) within the node.

The existence of multiple instances of the same whole offer or systemoverlay within a network, while not common, is not precluded. Thus, itmay be possible for the system identifier to be able to distinguishbetween different releases of a whole offer via different entries (e.g.,Offer X Release 1 v. Offer X Release 2) in the supported solutions listthat comprises the system identifier for a device. This may allow for aseamless WO upgrade, by way of identifying which network elements withina system are capable of running Release 2, and which network elementsare not. It is also possible to have different instances of the samerelease. For example, different nodes within an enterprise may be servedby different policy servers, resulting in multiple, coexisting wholeoffers of the same genre.

Network topology data may be collected in several ways. For example, acentral entity, such as an NMS or a service process may poll networkdevices within certain address ranges (or scopes) for neighborhood(device, link) information. Alternatively, an initiator node (such as arouter or a switch) within the network may initiate a low-resource layer2 network crawl with sophisticated duplicate request suppression andlooping suppression mechanisms.

In the network crawl, nodes may request and subsequently receivetopology/neighborhood information from their layer 2 neighbors andpropagate this information back to the initiator node (or nodes) whichserve as gateways to a centralized NMS or a service process. It shouldbe understood that link layer topology discovery protocols discover notonly switches, but also routers, servers, endpoints, and other networkdevices relevant to a whole offer strategy.

Another set of mechanisms for topology discovery may involve leveragingthe link state data collected via layer 3 routing protocols such asOSPF. A NMS or service process may collect this data from severalrouting nodes in order to construct a complete picture of the network.This is due to a routing node having complete link state information foronly a specific area of the network. The link-state also opaquelyadvertises system capability or belonging. Layer 3 topology maps addressrouting nodes and do not show switches, application servers, mediaservers, etc. which are relevant to solutions such as TrustSec andMediaNet.

Although the level of information gleaned from layer 2 discovery may bedifferent than the information gleaned via layer 3 discovery,embodiments of this disclosure are compatible with any of the networktopology methods described above and other known methods.

Once network topology data is collected, the annotation of nodes by amulti-element system identifier record may allow several innovative usecases. For example, topology layout and rendering engines can, on usercommand, collapse the network/subnet layout into an overlay system orsolution layout. The overlay system or solution layout may emphasizefunctions and relationships that signify a specific system or wholeoffer. In some embodiments, other renderings may show multiple overlayswithin the same network topology graph. Each overlay may be indicated bya different color. In some embodiments, system overlay information maybe viewable by right-clicking on nodes and/or links.

Based on the supported capabilities, the readiness of a network orsubnet to support a specific solution or a whole offer overlay may beassessed. This allows the additional identification of whether anoperating hybrid solution is complete (i.e., configured, ready, oroperational to have the complete system implemented network-wide.

Furthermore, the multi-element system identifier allows for thestreamlining of the assessment of the consistency, completeness, bestpractice conformance and regulatory compliance of a specific systemoverlay by allowing system-specific elements to be teased out from theirrelevant ones. This allows for quick and intelligent sifting whichfacilitates post-assessment optimization.

Identifying the elements of a solution also may aid whole offer billing.Element identification may also provide a correlation of whole offersupport entitlement with device-level support entitlement. This providesa solution capable of being integrated into a network community (orcloud networking environment) such that a network device can advise ofsystem faults.

Streamlining network-level troubleshooting by allowing support personnelto dynamically show and/or hide contexts. Contexts may include mobilitycontexts, energy management contexts, and other relevant contexts asneeded, regardless of how the information is presented.

Topology discovery schemes may also detect changes between successiveruns. These changes may result from node/link up/down transitions, andfrom moves, adds, changes, and deletes to the system. The ability toconveniently filter this information by whole offer and/or system (e.g.,TrustSec policy servers and switches) simplifies solutionadministration, debugging, triage, etc. Regardless of whetherwhole-offer based filtering is supported or not, a distinction betweenplanned and unplanned changes must be made on the basis of othercriteria, such as monitoring and configuration change management.

Monitoring systems, such as CISCO Mediatrace, may enable the isolationand troubleshooting of network degradation problems for data streams.The monitoring system runs may fetch the system identifier from variouslayer 2 and layer 3 nodes in the trace path. This opens up thepossibility of correlating system features support in various nodes inthe trace path with the measured performance (delay, jitter, loss, etc.)of the path segments associated with the nodes.

FIG. 2 is a flow chart illustrating embodiments of the presentdisclosure. Method 200 may begin at step 210 where network topologyinformation may be determined for a plurality of network devices on anetwork. Network topology information may be obtained through any of theprocedures described above or other appropriate discovery protocols.

Method 200 may then proceed to step 220. At step 220, system identifierinformation may be received from each of the plurality of networkdevices on the network. In some embodiments the system identifierinformation may comprise a list of network solutions that each networkdevice actually or potentially belongs to.

System identifier information may be obtained in a number of fashions.For example, the system identifier information may be received as aresponse to topology discovery queries performed by a neighbor networkdevice. In some embodiments, the response to topology discovery queriesmay be the result of a topology discovery protocol crawl. Alternatively,system identifier information may be received as a response to topologydiscovery poll initiated by a central server device on the network.

In some embodiments, the system identifier information may be receivedas a response to topology discovery poll initiated by an NMS serviceprocess. Alternatively, in some embodiments, the system identifierinformation may be received as a response to link-state advertisementsin a link-state routing protocol. The link-state routing protocol may beOSPF, for example.

Method 200 may then proceed to step 230. At step 230, the systemidentifier information may be flagged to indicate whether each solutionis an actual or a potential solution.

FIG. 3 is a flow chart illustrating embodiments of the presentdisclosure. Method 300 may begin at step 310 where a data structure maybe constructed mapping a topology of a plurality of network devices to alist comprising active and potentially active solutions available oneach network device on a network. In some embodiments, the active andpotentially active solutions available on each network device may bederived from capabilities and configuration data for each networkdevice. These capabilities and configuration data may be stored on amemory associated with a network device. In some embodiments, step 310may further include determining release version data for the determinedactive and potentially active solutions.

Method 300 may then proceed to step 320. At step 320, a flag may beappended to each determined active and potentially active solution,wherein the flag indicates whether the particular solution is currentlyactive or potentially active.

Method 300 may then proceed to step 330. At step 330, the data structuremay be displayed to a user in a plurality of display modes. Method 300may then proceed to step 340. At step 340, a whole offer upgrade may beimplemented based on the data structure.

FIG. 4 is a flow chart illustrating embodiments of the presentdisclosure. Method 400 may begin at step 410 where a network topologymay be discovered comprising a plurality of network devices on thenetwork.

Method 400 may proceed to step 420. At step 420 the network topology maybe annotated with a system identifier associated with each of theplurality of network devices, wherein the system identifier comprises alist of network solutions associated with the particular network device.

Next, at step 430 the annotated network topology may be applied toimplement a whole offer. At step 440, the network topology may bedisplayed to a user wherein the network topology comprises multipleoverlays indicated by different display colors. It should be understoodthat an end user may be either human or a machine interface.

Next, at step 450, the readiness of the network to support one of: aspecific solution and a whole offer overlay may be assessed based on theannotated network topology. As part of the assessment, solution-specificmay be teased out elements from non-solution specific elements.

Method 400 may proceed to step 460 where the whole offer supportentitlement to each device level support entitlement may be correlated.Subsequently, at step 470, a second annotated network topology may bedetermined. Changes between the first annotated network topology and thesecond annotated network topology may then be identified and assessed.

Finally, method 400 may proceed to step 480. At step 480, availablenetwork solutions for the plurality of network devices may be correlatedwith measured performance of one or more path segments connecting theplurality of network devices.

FIG. 5 is a block diagram of a system including network device 500.Consistent with embodiments of the present disclosure, theaforementioned memory storage and processing unit may be implemented ina network device, such as network device 500 of FIG. 5. Any suitablecombination of hardware, software, or firmware may be used to implementthe memory storage and processing unit. For example, the memory storageand processing unit may be implemented with network device 500 or any ofother network devices 518, in combination with network device 500. Theaforementioned system, device, and processors are examples and othersystems, devices, and processors may comprise the aforementioned memorystorage and processing unit, consistent with embodiments of the presentdisclosure.

With reference to FIG. 5, a system consistent with embodiments of thepresent disclosure may include a network device, such as network device500. In a basic configuration, network device 500 may include at leastone processing unit 502, a secure processing unit for decryption 520,and a system memory 504. Depending on the configuration and type ofnetwork device, system memory 504 may comprise, but is not limited to,volatile (e.g., random access memory (RAM)), non-volatile (e.g.,read-only memory (ROM)), flash memory, or any combination. System memory504 may include operating system 505, one or more programming modules506, and may include program data 507. Operating system 505, forexample, may be suitable for controlling network device 500's operation.Furthermore, embodiments of the present disclosure may be practiced inconjunction with a graphics library, other operating systems, or anyother application program and is not limited to any particularapplication or system. This basic configuration is illustrated in FIG. 5by those components within a dashed line 508.

Network device 500 may have additional features or functionality. Forexample, network device 500 may also include additional data storagedevices (removable and/or non-removable) such as, for example, magneticdisks, optical disks, or tape. Such additional storage is illustrated inFIG. 5 by a removable storage 509 and a non-removable storage 510.Computer storage media may include volatile and nonvolatile, removableand non-removable media implemented in any method or technology forstorage of information, such as computer readable instructions, datastructures, program modules, or other data. System memory 504, removablestorage 509, and non-removable storage 510 are all computer storagemedia examples (i.e., memory storage.) Computer storage media mayinclude, but is not limited to, RAM, ROM, electrically erasableread-only memory (EEPROM), flash memory or other memory technology,CD-ROM, digital versatile disks (DVD) or other optical storage, magneticcassettes, magnetic tape, magnetic disk storage or other magneticstorage devices, or any other medium which can be used to storeinformation and which can be accessed by network device 500. Any suchcomputer storage media may be part of device 500. Network device 500 mayalso have input device(s) 512 such as a keyboard, a mouse, a pen, asound input device, a touch input device, etc. Output device(s) 514 suchas a display, speakers, a printer, etc. may also be included. Theaforementioned devices are examples and others may be used.

Network device 500 may also contain a communication connection 516 thatmay allow device 500 to communicate with other network devices 518, suchas over a network in a distributed network environment, for example, anintranet or the Internet. Communication connection 516 is one example ofcommunication media. Communication media may typically be embodied bycomputer readable instructions, data structures, program modules, orother data in a modulated data signal, such as a carrier wave or othertransport mechanism, and includes any information delivery media. Theterm “modulated data signal” may describe a signal that has one or morecharacteristics set or changed in such a manner as to encode informationin the signal. By way of example, and not limitation, communicationmedia may include wired media such as a wired network or direct-wiredconnection, and wireless media such as acoustic, radio frequency (RF),infrared, and other wireless media. The term computer readable media asused herein may include both storage media and communication media.

As stated above, a number of program modules and data files may bestored in system memory 504, including operating system 505. Whileexecuting on processing unit 502 or secure processing unit fordecryption 520, programming modules 506 may perform processes including,for example, one or more method 200, 300, and 400's stages as describedabove. The aforementioned process is an example; processing unit 502 andsecure processing unit for decryption 520 may perform other processes.

Generally, consistent with per-subscriber stream management according toembodiments of this invention, program modules may include routines,programs, components, data structures, and other types of structuresthat may perform particular tasks or that may implement particularabstract data types. Moreover, embodiments may be practiced with othercomputer system configurations, including hand-held devices,multiprocessor systems, microprocessor-based or programmable consumerelectronics, minicomputers, mainframe computers, and the like.Embodiments of the present disclosure may also be practiced indistributed network environments where tasks are performed by remoteprocessing devices that are linked through a communications network. Ina distributed network environment, program modules may be located inboth local and remote memory storage devices.

Furthermore, embodiments of the present disclosure may be practiced inan electrical circuit comprising discrete electronic elements, packagedor integrated electronic chips containing logic gates, a circuitutilizing a microprocessor, or on a single chip containing electronicelements or microprocessors. Embodiments may also be practiced usingother technologies capable of performing logical operations such as, forexample, AND, OR, and NOT, including but not limited to mechanical,optical, fluidic, and quantum technologies. In addition, embodiments ofthe invention may be practiced within a general purpose computer or inany other circuits or systems.

Embodiments of the present disclosure, for example, may be implementedas a computer process (method), a network system, or as an article ofmanufacture, such as a computer program product or computer readablemedia. The computer program product may be a computer storage mediareadable by a computer system and encoding a computer program ofinstructions for executing a computer process. The computer programproduct may also be a propagated signal on a carrier readable by anetwork system and encoding a computer program of instructions forexecuting a computer process. Accordingly, aspects may be embodied inhardware and/or in software (including firmware, resident software,micro-code, etc.). In other words, embodiments of the present disclosuremay take the form of a computer program product on a computer-usable orcomputer-readable storage medium having computer-usable orcomputer-readable program code embodied in the medium for use by or inconnection with an instruction execution system. A computer-usable orcomputer-readable medium may be any medium that can contain, store,communicate, propagate, or transport the program for use by or inconnection with the instruction execution system, apparatus, or device.

The computer-usable or computer-readable medium may be, for example butnot limited to, an electronic, magnetic, optical, electromagnetic,infrared, or semiconductor system, apparatus, device, or propagationmedium. More specific computer-readable medium examples (anon-exhaustive list), the computer-readable medium may include thefollowing: an electrical connection having one or more wires, a portablecomputer diskette, a random access memory (RAM), a read-only memory(ROM), an erasable programmable read-only memory (EPROM or Flashmemory), an optical fiber, and a portable compact disc read-only memory(CD-ROM). Note that the computer-usable or computer-readable mediumcould even be paper or another suitable medium upon which the program isprinted, as the program can be electronically captured, via, forinstance, optical scanning of the paper or other medium, then compiled,interpreted, or otherwise processed in a suitable manner, if necessary,and then stored in a computer memory.

Embodiments of the present disclosure, for example, are described abovewith reference to block diagrams and/or operational illustrations ofmethods, systems, and computer program products according to embodimentsof per-subscriber stream management. The functions/acts noted in theblocks may occur out of the order as shown in any flowchart. Forexample, two blocks shown in succession may in fact be executedsubstantially concurrently or the blocks may sometimes be executed inthe reverse order, depending upon the functionality/acts involved.

While certain embodiments of the present disclosure have been described,other embodiments may exist. Furthermore, although embodiments have beendescribed as being associated with data stored in memory and otherstorage mediums, data can also be stored on or read from other types ofcomputer-readable media, such as secondary storage devices, like harddisks, floppy disks, or a CD-ROM, a carrier wave from the Internet, orother forms of RAM or ROM. Further, the disclosed methods' stages may bemodified in any manner, including by reordering stages and/or insertingor deleting stages, without departing from the invention.

While the specification includes examples, the invention's scope isindicated by the following claims. Furthermore, while the specificationhas been described in language specific to structural features and/ormethodological acts, the claims are not limited to the features or actsdescribed above. Rather, the specific features and acts described aboveare disclosed as example for embodiments of the present disclosure.

What is claimed is:
 1. A method comprising: receiving system identifierinformation from a plurality of network devices of a network, whereinthe system identifier information for a network device of the pluralityof network devices of the network comprises a list of network solutionsthat are available for the network device to belong to; constructing adata structure mapping a topology of the plurality of network devices,wherein constructing the data structure mapping the topology of theplurality of network devices comprises: annotating a first networksolution on the list of network solutions with an actual flag, theactual flag indicating that the first network solution is configured andoperationally active, and annotating a second network solution on thelist of network solutions with a potential flag, the potential flagindicating that the second network solution is configured butoperationally not active; determining, based on the data structuremapping the topology of the plurality of network devices, whether toimplement at least one of the following: a specific solution and a wholeoffer upgrade; and implementing, in response to determining to implementthe whole offer upgrade, the whole offer upgrade based on the datastructure, wherein implementing the whole offer upgrade comprisesdetermining to tease solution specific network devices from non-solutionspecific network devices.
 2. The method of claim 1, further comprisingderiving configured and operationally active and configured andoperationally not active solutions available on each network device fromcapabilities and configuration data for the each network device.
 3. Themethod of claim 2, wherein the capabilities and configuration data foreach network device are stored in a memory associated with each networkdevice.
 4. The method of claim 3, further comprising displaying the datastructure to a user.
 5. The method of claim 1, further comprisingdetermining a release version data for network solutions on the list ofnetwork solutions.
 6. The method of claim 1, further comprising creatinganother topology using annotated network solutions for the plurality ofnetwork devices.
 7. A non-transitory computer-readable medium thatstores a set of instructions which when executed perform a method, themethod comprising: receiving system identifier information from aplurality of network devices of a network, wherein the system identifierinformation for a network device of the plurality of network devices ofthe network comprises a list of network solutions that are available forthe network device to belong to; constructing a data structure mapping atopology of the plurality of network devices, wherein constructing thedata structure mapping the topology of the plurality of network devicescomprises: annotating a first network solution on the list of networksolutions with an actual flag, the actual flag indicating the firstnetwork solution is configured and operationally active, and annotatinga second network solution on the list of network solutions with apotential flag, the potential flag indicating the second networksolution is configured but operationally not active; determining, basedon the data structure mapping the topology of the plurality of networkdevices, whether to implement at least one of the following: a specificsolution and a whole offer upgrade; and implementing, in response todetermining to implement the whole offer upgrade, the whole offerupgrade based on the data structure, wherein implementing the wholeoffer upgrade comprises determining to tease solution specific networkdevices from non-solution specific network devices.
 8. Thenon-transitory computer-readable medium of claim 7, further comprisingderiving configured and operationally active and configured andoperationally not active solutions available on each network device fromcapabilities and configuration data for the each network device.
 9. Thenon-transitory computer-readable medium of claim 8, wherein thecapabilities and configuration data for the each network device arestored in a memory associated with the each network device.
 10. Thenon-transitory computer-readable medium of claim 9, further comprisingdisplaying the data structure to a user.
 11. The non-transitorycomputer-readable medium of claim 7, further comprising determining arelease version data for configured and operationally active andconfigured and operationally not active network solutions.
 12. Thenon-transitory computer-readable medium of claim 7, further comprisingcreating another topology using annotated network solutions for theplurality of network devices.
 13. An apparatus comprising: a memory; anda processor connected to the memory, wherein the processor is configuredto: receive system identifier information from a plurality of networkdevices of a network, wherein the system identifier information for anetwork device of the plurality of network devices of the networkcomprises a list of network solutions that are available for the networkdevice to belong to; construct a data structure mapping a topology ofthe plurality of network devices, wherein the processor being configuredto construct the data structure mapping the topology of the plurality ofnetwork devices comprises the processor being configured to: annotate afirst network solution on the list of network solutions with an actualflag, the actual flag indicating that the first network solution isconfigured and operationally active, and annotate a second networksolution on the list of network solutions with a potential flag, thepotential flag indicating that the second network solution is configuredbut operationally not active; determine, based on the data structuremapping the topology of the plurality of network devices, whether toimplement at least one of the following: a specific solution and a wholeoffer upgrade; and implement, in response to determining to implementthe whole offer upgrade, the whole offer upgrade based on the datastructure, wherein the processor being configured to implement the wholeoffer upgrade comprises the processor being configured to determine totease solution specific network devices from non-solution specificnetwork devices.
 14. The apparatus of claim 13, wherein the processor isfurther configured to derive configured and operationally active andconfigured and operationally not active solutions available on eachnetwork device from capabilities and configuration data for the eachnetwork device.
 15. The apparatus of claim 14, wherein the capabilitiesand configuration data for the each network device are stored in amemory associated with the each network device.
 16. The apparatus ofclaim 15, wherein the processor is further configured to display thedata structure to a user.
 17. The apparatus of claim 13, wherein theprocessor is further configured to determine a release version data forconfigured and operationally active and configured and operationally notactive solutions.
 18. The apparatus of claim 13, wherein the processoris further operative to create another topology using annotated networksolutions for the plurality of network devices.